====Discussion: What are Templates====

Also we need a "Last-install-backup" version, to solve the problem that Gilletarom had with a new version, overwriting his v4.8.6 opencpn.ini.

"We may need a new start-up switch feature: OpenCPN.exe 'user-settings-name'. Then every user can start there own session of O by different shortcuts."
What about just suggesting this type of use in the manual and having a couple of examples in the release version with

    Fall-back-to-basic   (Best configuration for beginners)
    Last-install-backup  (Settings for the previous installation)
    oesenc-configuration (Best start configuration for oesenc)
    Hakan-Nightwatch  (night settings)
    Hakan-Daywatch   (day settings)
    Hubert-Ecdis-Day-Spain (Ecdis mode, daytime, Spanish Inland waterways) 

Many uses.

Agreed.  Navobj is shared. I believe that at some point Navobj needs greater functionality, for saving backups, edit, rename, join, separate, etc.

On 10/3/2018 9:55 AM, S/Y Momo/Håkan wrote:
> Rick..
> Since Hubert showed some initial discussions we once had maybe my thoughts could help you to your own mind about this topic.
> And to enlace the possible features?
>
> Håkan
>
> Extracts from earlier discussions:
>  The following are in other words my thoughts as entries to this discussion.
>
> -  User settings saved as different set of configurations in general:
> I see that as a very good idea. Different individually named set-ups can be very useful. Both for different type of navigation aids for different waters for a single skipper and for individual set-ups for different persons while on watch. Though we do need a fall-back-to-basics. I think that's what you mentioned as a template?
> Now we've to discuss;
>
> -  How to create and activate saved user settings.
> -  What settings and data should be included in each user setting.
> -  What will be included in a fall-back-to-basics settings.
>
>     Create and activate user settings
>     A new set of user settings would be handled in a an own tools tab or similar.
>     Every new set of settings must be given a name and inherit all present settings. Compare creating a new Git branch. What data and settings to be included in the new set I'll discuss in paragraph 2.
>     I think the thoughts expressed here implies individual config files for each user settings. It may be called like opencpn_'name'.ini/config. The "old" opencpn-config would still be alive but the only duty for this is to detect last used user settings file and ships position. Last viewport and chart group would be read from the user settings file.
>     O will always start loading the user settings in operation at close down.
>     The "create-new" user settings button will be functional only when some settings are changed during a single O-session. A change of any setting(s) are though not restored at next start if not present user settings are explicitly updated/committed or saved to a new user setting. This implies that any playing or dummy run with settings will be restored at O re-start if not saved. (Here we can reflect whether a not updated change will render a pop-up question to save changed settings at O closure?)
>     From the same tools tab the user can also switch between previously saved settings. The first on that list list will always be the "Fall-back-to-basics".
>     We may need a new start-up switch feature: OpenCPN.exe 'user-settings-name'. Then every user can start there own session of O by different shortcuts.
>
>     Settings and data to be included in each user setting.
>     Settings are all configurable settings in the following tool tabs; Display (all sub-tabs), Vector charts display, Chart groups, Ships (all sub-tabs), User Interface, Plugins-activated or not.
>     There are also settings in the config file not reflected in any tools-tab. Experienced users handle these by editing the config file. There will be no change to this procedure but he or she has to be aware of which user config file to edit. Maybe not feasible for the every day user but they are not editing any config file.
>
>     Data are charts and what's saved to navobj.xml. (MMSINAME will be the same for all user settings.)
>     Charts can be tricky in this matter. My initial thoughts are that all charts added, deleted or changed to "Chart files" would be reflected to all filed user settings. Any individual user settings for available charts would be handled by chart groups.
>     Routes, tracks and WPs and what's saved in navobj.xml could be individual for each user setting but here we may run into problem. Even if a route is made by one user setting the others may want to use it as well. Not less if the crew on next watch use another user setting they will for sure use the same route. If we include navobj.xml in the user settings there would be need for extensive copying features and complicated questions upon a route creation if it shall be included also in other user settings or not. So - navobj.xml would be one file shared by all settings.
>
>     Fall-back-to-basics settings.
>     These are the initial settings at first start-up. The config file can be called opencpn_default.ini/config.
>     I think we have a rather good understanding of "basic" settings already. I suggest the user should not be able to change this by any user settings. If any experienced user wants to "hack" it like we do today it's up to each and every one.
>     We may consider an easy accessible "Fall-back-to.basic" function without using the tools-user settings-tab mentioned above. A new tool/menu?